Mission Management Team

The Mission Management Team (MMT) was the group responsible for coordinating decisions about the Columbia mission. In the book’s account, its failure was not simply a shortage of information or expertise: engineers had raised concerns about the foam strike, but the team’s hierarchy and discussion practices prevented those concerns from becoming part of a genuinely collective judgment. Its case shows the difference between assembling knowledgeable people and designing a process that lets their knowledge matter.

Role and Decision Structure

The MMT was meant to bring together mission-related assessments, but its members’ views were never combined into a decision through a vote. They reported on different aspects of the mission; the team did not formally aggregate their opinions. The distinction is central to the book’s argument: a group does not gain the benefits of collective intelligence merely by placing individuals in the same organizational structure. If a team is advisory, or if its members’ judgments remain separate, the organization has not made use of the group’s combined knowledge.

The book contrasts this failure of aggregation with the wider principle that a capable group needs both decentralized expertise and a way to make individual knowledge collectively useful. Decentralization can preserve independence and specialization, but without channels that carry information across the system, valuable findings may remain isolated. The MMT’s problem was therefore not that every decision should have been removed from the team or handed to a single central authority; it was that the team did not make its members’ judgments count together.

Foam-Strike Discussion

The team’s January 24 meeting displayed how its process narrowed the available discussion. When Don McCormack summarized the Debris Assessment Team’s findings, he did not present the supporting analysis or explain whether the assessment had divided the DAT. No MMT member asked to see the study or questioned the uncertainties McCormack had mentioned. Linda Ham was anxious to resolve the issue and treated the summary as settling it, repeating, “No burn-through, means no catastrophic damage”. Her brisk conclusion helped close down debate rather than invite examination of the analysis.

The engineers on the DAT had serious qualms about the foam strike from the beginning. In particular, they said that they needed images of the Orbiter’s wing before they could make a truly informed assessment. Their request and their concerns did not receive a serious hearing from the MMT. The issue was not simply that relevant expertise was absent: specialized knowledge existed within the broader team, but the process did not bring it into the decision in a form that could challenge the prevailing conclusion.

Hierarchy and Deliberation

Although NASA was often regarded as meritocratic and bottom-up, the account describes it as deeply hierarchical. That organizational reality shaped whose concerns were heard: the DAT engineers’ doubts did not carry enough authority to redirect the MMT’s discussion. The team’s meetings were, paradoxically, both overstructured and understructured. Much of the conversation followed a narrow pattern in which Ham asked a question and another person answered; yet no one was specifically asked to assess key questions or offer a view. A meeting can therefore look orderly while still drawing on only a limited supply of analysis.

The book emphasizes that productive deliberation requires both a clear agenda and active efforts by leaders to make sure participants have a chance to speak. The MMT lacked that balance. It also began with a conclusion and interpreted incoming information to fit it, rather than using new evidence to test the conclusion. This made it harder for the team to incorporate information that was not already shared or that contradicted its established view.

Failure to Aggregate

The MMT never voted on anything. Its members provided separate reports, but their actual opinions were not brought together through a collective decision. That omission mattered independently of what happened to Columbia: even if the shuttle had returned safely, the team would still have failed to use the decision-making advantage that a team is supposed to provide. Group deliberation can be valuable and need not be slower or less capable than individual judgment, but it requires a method for aggregating the group’s views.

The MMT’s story thus joins the book’s broader distinction between information-sharing and collective judgment. Linking people or circulating reports may help information move, but it does not by itself make a group wise. The team’s specialized knowledge, including the engineers’ demand for wing images, needed a process that preserved disagreement, solicited independent assessments, and made the resulting judgments count. Without those steps, hierarchy and premature closure left the group with information it did not effectively use.